Release 10.1A: OpenEdge Getting Started:
WebSpeed Essentials

Development and deployment shared configuration

When a company develops its own applications, it can have networks that are used for development, testing, and deployment simultaneously.

Figure 4–6 shows the products installed in a shared development and deployment network.

Note: The WebSpeed Broker and the WebSpeed Agents it controls are collectively referred to as the WebSpeed Transaction Server in this figure.

Figure 4–6: Development and deployment shared configuration

In this configuration, the dedicated Web server machine, Neptune, has two Web servers installed. One Web server handles the development workload, and the other handles the deployment workload. This allows the developers to experiment with the environment without bringing down the deployment side. Each of the Web servers requires its own WebSpeed Messenger, but only the development Web server needs the WebSpeed WebTools.

On the development side, the Messenger routes requests to the NameServer on Triton. Triton’s NameServer only has the WebSpeed Transaction Servers on Proteus registered, so it looks there for a Transaction Server to handle the request. Proteus has the WebSpeed Enterprise Transaction Server and either the OpenEdge Enterprise RDBMS or a non-Progress data source installed on it.

On the deployment side, that Messenger routes requests to the NameServer on Galatea. Galatea has the WebSpeed Enterprise Transaction Server installed. The deployment side uses a dedicated machine, Nereid, to hold its data source (that is, the OpenEdge Enterprise RDBMS or a non-Progress data source).

To set up a development and deployment shared configuration:

Install two copies of your Web server on Neptune.
Install the Enterprise NameServer on Triton.
Install the WebSpeed Enterprise Transaction Server on Proteus.
Install the WebSpeed Messenger on Neptune using the development Web server’s Document Root directory and scripts path.
Configure the Development Web server’s WebSpeed Messenger on Neptune to pass requests to Triton’s NameServer.
Install OpenEdge Studio or the WebSpeed Workshop on Thalassa and your other workstations, according to your development needs.
Install the WebSpeed Messenger on Neptune using the deployment Web server’s Document Root directory and scripts path.
Note: Since the WebSpeed WebTools are only meant for developers, you should remove access to them through the deployment Web server. During the Messenger-only installation, do not choose the option to either create a virtual directory or copy the static HTML files.
Install the WebSpeed Enterprise Transaction Server on Galatea.
Configure the Deployment Web server’s WebSpeed Messenger on Neptune to pass requests to Galatea’s NameServer.
Install the appropriate data source components on Proteus and Nereid. This depends on what you are planning to use as your data source:
If you use the OpenEdge Database, install the OpenEdge Enterprise RDBMS.
If you connect to a non-OpenEdge data source, install the appropriate OpenEdge DataServers. See the appropriate OpenEdge DataServer guide for details.
Install your r-code on Galatea and include its location in the WebSpeed agent’s PROPATH.
Copy any Java applet, static HTML, and .gif files that your applications must the deployment Web server’s /docroot/webspeed directory on Neptune.

Beyond the basic installation

As described, this configuration uses the components for a heavy load system. If you expect a light load on the network, you might consider installing the WebSpeed Transaction Server and OpenEdge Workgroup RDBMS instead of the Enterprise Transaction Server and OpenEdge Enterprise RDBMS. The WebSpeed Transaction Server can handle up to 50 WebSpeed Agents. The OpenEdge Workgroup RDBMS can handle up to 65 connections.

You can expand the capacity of either side of this configuration by adding new server machines with the same products installed. Register the WebSpeed Transaction Servers on the new machines with the NameServer that is handling the Transaction Servers for that side.

When you expect heavy loads on your network or want to increase its fault tolerance, you might want to add the load balancing option for the NameServer. If you deploy several WebSpeed Transaction Servers that support the same application service, you can use load balancing to control how the load is spread over them. See the "Understanding the NameServer’s load balancing option" section.

If you are going to use a non-OpenEdge database, you must install the appropriate DataServer on the Nereid and Proteus servers.

Development startup sequence

After you have installed and configured everything, you can start your WebSpeed environment.

To start the Development side of this shared configuration:

Start the AdminServers on Triton and Proteus.
Note: Once the AdminServers have started, you can use the Progress Explorer from any machine to start other components on these machines.
Start the data source (and the data server broker, if needed) on Proteus in multi-user mode.
Start the NameServer on Triton.
Start the WebSpeed Transaction Server on Proteus.
Start the development Web server on Neptune.
Start an AppBuilder on a workstation (like Thalassa) as needed.
Start a Web browser on a workstation by choosing the WebTools from the AppBuilder’s Tools menu as needed.

Deployment startup sequence

After you have installed and configured everything, you can start your WebSpeed environment.

To start the Deployment side of this shared configuration:

Start the AdminServers on Galatea and Nereid.
Note: Once the AdminServers have started, you can use the Progress Explorer from any machine to start other components on these machines.
Start the data source in multi-user mode on Nereid.
Start the NameServer on Galatea.
Start the WebSpeed Transaction Server on Galatea.
Start the deployment Web server on Neptune.
Note: If one of the data sources fails, you should stop all the WebSpeed Transaction Servers supporting applications that use that data source. Bring the data source back up and then restart the Transaction Servers. This helps ensure data integrity.